- software requirements document
- Программирование: документирование требований к ПО, документирование требований к программному обеспечению
Универсальный англо-русский словарь. Академик.ру. 2011.
software requirements document
Смотреть что такое "software requirements document" в других словарях:
Product requirements document — A PRD is often created after a market requirements document (MRD) has been written and been given approval by management, and is usually written before (or at least concurrently with) a technical requirements document. It is designed to allow… … Wikipedia
User requirements document — The user requirements document (URD) is a document used in software engineering that specifies the requirements the user expects from software to be constructed in a software project.An important and difficult step of designing a software product … Wikipedia
Software documentation — or source code documentation is written text that accompanies computer software. It either explains how it operates or how to use it, and may mean different things to people in different roles. Contents 1 Role of documentation in software… … Wikipedia
Software prototyping — Software prototyping, a possible activity during software development, is the creation of prototypes, i.e., incomplete versions of the software program being developed.A prototype typically simulates only a few aspects of the features of the… … Wikipedia
Software product management — is the process of managing software that is built and served as a product as opposed to a serviceoftware productsA software product is typically a single application or suite of applications built by a software company to be used by *many*… … Wikipedia
Requirements traceability — is a sub discipline of requirements management within software development and systems engineering. Requirements traceability is concerned with documenting the life of a requirement. It should be possible to trace back to the origin of each… … Wikipedia
Software design — is a process of problem solving and planning for a software solution. After the purpose and specifications of software are determined, software developers will design or employ designers to develop a plan for a solution. It includes low level… … Wikipedia
Document composition — is the process of dynamically composing Documents according to the Business Requirements.Document Composition is primarily used by the Organization which requires Communication with their Customers in a large daily basis.Document Composition… … Wikipedia
Requirements management — The purpose of Requirements management is to assure the organization leverages to the expectations of its customers, internal or external stakeholders. It focuses on requirements as the element capturing these expectations, and thus, as a focal… … Wikipedia
Software inspection — Inspection in software engineering, refers to peer review of any work product by trained individuals who look for defects using a well defined process. An inspection might also be referred to as a Fagan inspection after Michael Fagan, the… … Wikipedia
Software Engineering Body of Knowledge — The Software Engineering Body of Knowledge (SWEBOK) is a product of the Software Engineering Coordinating Committee. The IEEE Computer Society is also involved.The software engineering body of knowledge is an all inclusive term that describes the … Wikipedia
